Multi-Carrier Rel-19
Please refer to RP-242408
for detailed scope of the WI for Multi-Carrier Enhancements for NR Phase 2.
R1-2409227 Session
notes for 9.12 (Multi-Carrier Enhancements for NR Phase 2) Ad-Hoc Chair (CMCC)
Friday decision: The session notes are endorsed and contents reflected below.
[118bis-R19-MCE] – Haipeng (Lenovo)
Email discussion on Rel-19 multi-carrier
enhancement
-
To be used for sharing updates on
online/offline schedule, details on what is to be discussed in online/offline
sessions, tdoc number of the moderator summary for online session, etc
R1-2408261 Work
plan for Rel-19 Multi-carrier enhancements Lenovo
Decision:
The document is noted.
Including scheduling of different
SCS/carrier types and (one
or) multiple PUSCHs/PDSCHs per scheduled cell.
R1-2407688 Discussion
on Rel-19 Multi-carrier enhancements Huawei, HiSilicon
R1-2407726 Discussion
on multi-cell PUSCH/PDSCH scheduling with a single DCI Spreadtrum
Communications
R1-2407810 Discussion
on multi-cell PUSCH/PDSCH scheduling with a single DCI ZTE
Corporation, Sanechips
R1-2407883 Discussion
on enhancement of multi-cell PUSCH/PDSCH scheduling with a single DCI vivo
R1-2407925 Discussion
on multi-cell PUSCH/PDSCH scheduling with a single DCI CMCC
R1-2408038 Discussion
on multi-cell PUSCH/PDSCH scheduling with a single DCI CATT
R1-2408157 Discussion
of multi-cell scheduling with a single DCI OPPO
R1-2408262 Discussion
on multi-cell scheduling with a single DCI Lenovo
R1-2408364 Discussion
on multi-carrier enhancements for NR Phase 2 Panasonic
R1-2408492 On
multi-cell PUSCH/PDSCH scheduling with single DCI Apple
R1-2408668 Enhancements
for multi-cell PUSCH/PDSCH scheduling Samsung
R1-2408669 Discussion
on Multi-cell PUSCH/PDSCH scheduling with a single DCI TCL
R1-2408683 Discussion
on single DCI based multi-cell scheduling for Rel-19 LG
Electronics
R1-2408713 Multi-Carrier
enhancements initial views MediaTek Inc.
R1-2408805 Discussion
on multi-cell PUSCH/PDSCH scheduling with a single DCI NTT DOCOMO,
INC.
R1-2408872 Multi-cell
PUSCH/PDSCH scheduling with a single DCI Qualcomm Incorporated
R1-2408893 Multi-cell
PxSCH scheduling with a single DCI Ericsson
Monday session
R1-2408260 On
Rel-19 Multi-carrier enhancements for NR Phase 2 Nokia
Decision:
The document is noted.
R1-2409162 Feature
lead summary#1 on multi-cell scheduling with a single DCI Moderator
(Lenovo)
Presented in Tuesday session.
R1-2409163 Feature
lead summary#2 on multi-cell scheduling with a single DCI Moderator
(Lenovo)
From Wednesday session
Agreement
For multiple PUSCHs/PDSCHs scheduled on a
cell by a DCI format 0_3/1_3,
·
Common FDRA
is applied to the PUSCHs/PDSCHs on the cell as Rel-16/17 multi-PUSCH/PDSCH
scheduling.
·
Common MCS
is applied to the PUSCHs/PDSCHs on the cell as Rel-16/17 multi-PUSCH/PDSCH
scheduling.
·
HARQ
process number indicated for the cell is applied to the first scheduled
PUSCH/PDSCH and then incremented by 1 for subsequent PUSCHs/PDSCHs on the cell
(with modulo operation if needed) as Rel-16/17 multi-PUSCH/PDSCH scheduling.
Agreement
In DCI format 0_3/1_3, for each block of
NDI field, consider the following options:
·
Option 1: the number of
bits is equal to the maximum number of schedulable PUSCHs/PDSCHs on the
corresponding cell by the DCI format 0_3/1_3.
·
Option 2: the number of
bits is equal to the actual number of scheduled PUSCHs/PDSCHs on the
corresponding cell by the DCI format 0_3/1_3.
·
Option 3: if the number of
scheduled PUSCH/PDSCH is 1, then one bit NDI is applied; otherwise, option 1 is
applied.
Agreement
In DCI format 0_3/1_3, for each block of RV
field, consider the following options:
·
Option 1: the number of
bits is determined based on the maximum number of schedulable PUSCHs/PDSCHs on
the corresponding cell by the DCI format 0_3/1_3 and number of bits for RV configured
for the corresponding cell.
·
Option 2: the number of
bits is determined based on the actual number of scheduled PUSCHs/PDSCHs on the
corresponding cell by the DCI format 0_3/1_3 and number of bits for RV configured
for the corresponding cell.
·
Option 3: if the number of
scheduled PUSCH/PDSCH is 1, then option 2 is applied; otherwise, option 1 is
applied.
Agreement
A single TDRA field in DCI format 0_3/1_3 indicates
one row from a joint TDRA table.
·
Each row in the table
contains only one TDRA index for each BWP of each cell within the set of cells.
Each TDRA index points to one or multiple time domain resource allocations in
the TDRA table applicable for multi-PUSCH/PDSCH scheduling by DCI format
0_3/1_3 for the corresponding cell.
R1-2409164 Feature
lead summary#3 on multi-cell scheduling with a single DCI Moderator
(Lenovo)
From Thursday session
Agreement
·
Time domain HARQ-ACK
bundling is supported.
Agreement
- Consider at least the case
that up to two different SCS can
be scheduled by a DCI format 0_3/1_3 in Rel-19.
- Consider at least
the following cases for scheduled cells in Rel-19:
- Case 1: A DCI
format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR1 licensed FDD cell(s) with
SCS1 and FR1 licensed TDD cell(s) with SCS2.
- SCS1 can be same
or different to SCS2.
- Case 2: A DCI
format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR1 licensed FDD cell(s) with
SCS1 and FR2-1 cell(s) with SCS2.
- SCS1 can be same
or different to SCS2.
- Case 3: A DCI
format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR1 licensed TDD cell(s) with
SCS1 and FR2-1 cell(s) with SCS2.
- SCS1 can be same
or different to SCS2.
- Case 4: A DCI
format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR1 licensed FDD cell(s) with
different SCS.
- Case 5: A DCI
format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR1 licensed TDD cell(s) with
different SCS.
- Case 6: A DCI
format 0_3/1_3 scheduling PUSCHs/PDSCHs on FR2-1 cell(s) with different
SCS.
Final summary in R1-2409166.
Please refer to RP-242408 for detailed scope of
the WI for Multi-Carrier Enhancements for NR Phase 2.
R1-2410849 Session notes for 9.12 (Multi-Carrier Enhancements for NR
Phase 2) Ad-Hoc Chair (CMCC)
Friday decision: The session notes are endorsed and contents reflected below.
[119-R19-MCE] – Haipeng (Lenovo)
Email discussion on Rel-19 multi-carrier
enhancement
-
To be used for sharing
updates on online/offline schedule, details on what is to be discussed in
online/offline sessions, tdoc number of the moderator summary for online
session, etc
Including scheduling of different
SCS/carrier types and (one
or) multiple PUSCHs/PDSCHs per scheduled cell.
R1-2409404 Discussion on Rel-19 Multi-carrier enhancements Huawei,
HiSilicon
R1-2409484 Discussion on multi-cell scheduling with a single DCI Lenovo
R1-2409532 Discussion on multi-cell PUSCH/PDSCH scheduling with a
single DCI CMCC
R1-2409541 Discussion on multi-cell PUSCH/PDSCH scheduling with a
single DCI ZTE Corporation, Sanechips
R1-2409619 Enhancements for multi-cell PUSCH/PDSCH scheduling Samsung
R1-2409655 Discussion on multi-cell PUSCH/PDSCH scheduling with a
single DCI Spreadtrum, UNISOC
R1-2409703 Discussion on enhancement of multi-cell PUSCH/PDSCH
scheduling with a single DCI vivo
R1-2409716 On Rel-19 Multi-carrier enhancements for NR Phase 2 Nokia
R1-2409828 On multi-cell PUSCH/PDSCH scheduling with single DCI Apple
R1-2409868 Discussion on multi-cell scheduling with a single DCI NEC
R1-2409931 Discussion on multi-cell PUSCH/PDSCH scheduling with a
single DCI CATT
R1-2410010 Discussion on multi-carrier enhancements for NR phase 2 China
Telecom
R1-2410066 Discussion on Multi-cell PUSCH/PDSCH scheduling with a
single DCI TCL
R1-2410100 Discussion of multi-cell scheduling with a single DCI OPPO
R1-2410250 Discussion on multi-carrier enhancements for NR Phase 2 Panasonic
R1-2410281 Discussion on multi-cell PUSCH/PDSCH scheduling with a
single DCI ETRI
R1-2410298 Discussion on single DCI based multi-cell scheduling for
Rel-19 LG Electronics
R1-2410408 Discussion on multi-cell PUSCH/PDSCH scheduling with a
single DCI NTT DOCOMO, INC.
R1-2410500 Multi-cell PUSCH/PDSCH scheduling with a single DCI Qualcomm
Incorporated
R1-2410509 Multi-cell PUSCH/PDSCH scheduling with a single DCI MediaTek
Inc.
R1-2410536 Multi-cell PxSCH scheduling with a single DCI Ericsson
R1-2410729 Feature lead summary#1 on multi-cell scheduling with a
single DCI Moderator (Lenovo)
From Monday session
Agreement
·
Time-domain HARQ-ACK
bundling is configured per cell as Rel-17.
R1-2410730 Feature lead summary#2 on multi-cell scheduling with a
single DCI Moderator (Lenovo)
From Tuesday session
Agreement
·
Specification supports the maximum number of PUSCHs/PDSCHs for a scheduled cell by a DCI format 0_3/1_3 is 8.
·
Payload size of a DCI
format 0_3/1_3 exceeding 140 is not supported in Rel-19.
R1-2410731 Feature lead summary#3 on multi-cell scheduling with a
single DCI Moderator (Lenovo)
From Wednesday session
Agreement
Type-2 HARQ-ACK codebook is generated by concatenating a first sub-codebook and a second
sub-codebook.
·
The first sub-codebook
comprises HARQ-ACK information bits for PDSCH(s) scheduled by DCI(s) with each
scheduling a single PDSCH, or each scheduling a single cell with multiple
PDSCHs on it and nrofHARQ-BundlingGroups configured as 1, and HARQ-ACK
information bit(s) for DCI(s) having associated HARQ-ACK information without
scheduling PDSCH reception.
·
The second sub-codebook
comprises HARQ-ACK information bits for PDSCHs scheduled by DCI(s) with each
scheduling more than one cell, or each scheduling a single cell with multiple
PDSCHs on it without nrofHARQ-BundlingGroups or nrofHARQ-BundlingGroups
configured larger than 1.
·
Separate DAI counting is
applied for DCI(s) associated with the first sub-codebook and DCI(s) associated
with the second sub-codebook as
Rel-18.
·
Note: For providing
HARQ-ACK information corresponding to SCell dormancy indication, the UE assumes
that the UE receives a PDSCH on the serving cell associated with fields in DCI
format 1_3 used for SCell dormancy indication as Rel-18.
R1-2410732 Feature lead summary#4 on multi-cell scheduling with a
single DCI Moderator (Lenovo)
From Thursday session
Agreement
- For the second sub-codebook,
the number of HARQ-ACK information bits for each DCI format 1_3 is equal
to M,
to select one of the following options.
- Option 1: M is the maximum
number of HARQ-ACK information bits which can
be generated for a DCI format 1_3 across all the configured cell
set(s) in the PUCCH group for the UE. M is implicitly derived based on
RRC configuration.
- Option 2: M is explicitly
configured by RRC parameter for the PUCCH group.
- Other options are not
precluded.
Agreement
- For NDI indication in DCI
format 0_3/1_3 for TB1,
further study
- Option 1: For each block of
NDI field, the number of bits is equal to the maximum number of
schedulable PUSCHs/PDSCHs on the
corresponding cell by the DCI format 0_3/1_3.
- Maximum number of schedulable PUSCHs/PDSCHs on the
corresponding cell is determined by TDRA table for the cell.
- Option 2a: Total number of bits of the NDI field is equal to the
maximum number of schedulable PUSCHs/PDSCHs by the DCI format 0_3/1_3 across all the
co-schedulable cells.
- The number of bits of a
block of NDI field corresponding to a scheduled cell is equal to the
actual number of the scheduled PUSCHs/PDSCHs by the DCI format 0_3/1_3
on the cell.
- Some reserved bits are
needed when the actual number of the scheduled PUSCHs/PDSCHs by the DCI
format 0_3/1_3 is smaller than the maximum number of schedulable PUSCHs/PDSCHs by the DCI format
0_3/1_3
across all the co-schedulable cells.
- Other options are not
precluded.
- Note: For Option 1 and 2a, DCI format 0_3/1_3
has
blocks of NDI
field for TB1, same as in Rel-18.
Agreement
- For RV indication in DCI
format 0_3/1_3 for TB1, further
study
- Option 1: For each block of
RV field, the number of bits is equal to the maximum number of
schedulable PUSCHs/PDSCHs on the
corresponding cell by the DCI format 0_3/1_3 and number of bits for RV
configured for the cell.
- Maximum number of schedulable PUSCHs/PDSCHs on the
corresponding cell is determined by TDRA table for the cell.
- Option 2a: Total number of bits of the RV field is determined
based on the maximum number of schedulable PUSCHs/PDSCHs by the DCI format
0_3/1_3
across all the co-schedulable cells.
- The number of bits of a
block of RV field corresponding to a scheduled cell is determined based
on the actual number of the scheduled PUSCHs/PDSCHs by the DCI format
0_3/1_3 on the cell and number of bits for RV configured for the cell.
- Some reserved bits are
needed when the actual number of the scheduled PUSCHs/PDSCHs by the DCI
format 0_3/1_3 is smaller than the maximum number of schedulable PUSCHs/PDSCHs by the DCI format
0_3/1_3
across all the co-schedulable cells.
- Other options are not
precluded.
- Note: For Option 1 and 2a, DCI format 0_3/1_3
has blocks of RV field
for TB1, same as in Rel-18.
Final summary in R1-2410905.
R1-2501551 Session notes for 9.12 (Multi-Carrier Enhancements for NR
Phase 2) Ad-Hoc Chair (CMCC)
Friday decision: The session notes are endorsed and contents reflected below.
Please refer to RP-242904 for detailed scope of
the WI for Multi-Carrier Enhancements for NR Phase 3.
[120-R19-MCE] – Haipeng (Lenovo)
Email discussion on Rel-19 multi-carrier
enhancement
-
To be used for sharing updates on
online/offline schedule, details on what is to be discussed in online/offline
sessions, tdoc number of the moderator summary for online session, etc
R1-2500065 On Rel-19 Multi-carrier enhancements Nokia
R1-2500092 Discussion on Rel-19 Multi-carrier enhancements Huawei,
HiSilicon
R1-2500139 Discussion on multi-cell scheduling with a single DCI Lenovo
R1-2500147 Discussion on multi-cell PUSCH/PDSCH scheduling with a
single DCI ZTE Corporation, Sanechips
R1-2500187 Discussion on multi-cell PUSCH/PDSCH scheduling with a
single DCI Spreadtrum, UNISOC
R1-2500212 Discussion on multi-cell PUSCH/PDSCH scheduling with a
single DCI CATT
R1-2500271 Discussion on multi-carrier enhancements for NR phase 3 China
Telecom
R1-2500306 Discussion on multi-cell PUSCH/PDSCH scheduling with a
single DCI CMCC
R1-2500371 Discussion on enhancement of multi-cell PUSCH/PDSCH
scheduling with a single DCI vivo
R1-2500461 Discussion of multi-cell scheduling with a single DCI OPPO
R1-2500808 On multi-cell PUSCH/PDSCH scheduling with single DCI Apple
R1-2500818 Discussion on multi-carrier enhancements for NR Phase 3 Panasonic
R1-2500871 Enhancements for multi-cell PUSCH/PDSCH scheduling Samsung
R1-2500923 Discussion on multi-cell PUSCH/PDSCH scheduling with a
single DCI ETRI
R1-2500960 Discussion on single DCI based multi-cell scheduling for
Rel-19 LG Electronics
R1-2500985 Discussion on Multi-cell PUSCH/PDSCH scheduling with a
single DCI TCL
R1-2501033 Multi-cell PUSCH/PDSCH scheduling with a single DCI MediaTek
Inc.
R1-2501178 Multi-cell PUSCH/PDSCH scheduling with a single DCI Qualcomm
Incorporated
R1-2501220 Discussion on multi-cell PUSCH/PDSCH scheduling with a
single DCI NTT DOCOMO, INC.
R1-2501345 Multi-cell PxSCH scheduling with a single DCI Ericsson
R1-2501374 Feature lead summary#1 on multi-cell scheduling with a
single DCI Moderator (Lenovo)
From Monday session
Agreement
- For determining the timing of a PUCCH
carrying HARQ-ACK information corresponding to a set of co-scheduled
PDSCHs by a DCI format 1_3, follow Rel-18 operation.
- If the UE is not provided subslotLengthForPUCCH,
the DL slot 𝑛𝐷
is the DL slot ending last, amongst the DL slots
where the more than one PDSCH are scheduled by the DCI format 1_3.
- FFS: RAN1 spec impact till
RAN1#120-bis
- If the UE is
provided subslotLengthForPUCCH, no spec
change is necessary.
- Note: Specification
of this feature shall not impact the existing UE processing PDSCH timeline
requirement for any individual PDSCH, as specified in 5.3.1 of TS38.214.
Agreement
For the second sub-codebook, the number of
HARQ-ACK information bits for each DCI format 1_3 is equal to M.
- M is the maximum
number of HARQ-ACK information bits which can be generated for a DCI
format 1_3 across all the configured cell set(s) in the PUCCH group for
the UE. M is implicitly derived based on RRC configuration.
Agreement
For NDI indication in DCI format 0_3/1_3
for a TB,
·
Option 1 is adopted.
Agreement
For RV indication in DCI format 0_3/1_3 for a TB,
·
Option 1 is adopted.
Agreement
For multi-PUSCH/PDSCH scheduling using a
DCI format 0_3/1_3, 1 bit RV indication is determined according to Table
7.3.1.2.3-1 of TS 38.212.
·
Note: This is aligned with
Rel-18 DCI format 0_3/1_3 for cells configured with 1 bit RV by numberOfBitsForRV-DCI-0-3/1-3.
Agreement
For the second sub-codebook, the HARQ-ACK
information bits for a DCI format 1_3 are ordered firstly according to same
ordering as in Rel-17 multi-PDSCHs scheduling for PDSCH
receptions on a same serving cell, then according to ascending order of
associated serving cell indexes.
R1-2501375 Feature lead summary#2 on multi-cell scheduling with a
single DCI Moderator (Lenovo)
From Tuesday session
Agreement
For Type-1C fields in DCI format 0_3, when
the TDRA field indicates more than one scheduled PUSCHs on the scheduled cell
with the smallest cell index:
·
The CSI request field applies to the PUSCH determined based on Rel-17
multi-PUSCH scheduling on same serving cell.
·
Note for background: When the TDRA field of DCI
format 0_3 indicates only one scheduled PUSCH on the scheduled cell with the
smallest cell index, DCI interpretation and UE procedure is same as in Rel-18.
Working Assumption
For a DCI format 1_3 with fields repurposed
for SCell dormancy indication and scheduling one or more PDSCHs, if TDRA field
indicates multiple SLIVs for the serving cell with smallest serving cell index
with invalid FDRA, the HARQ-ACK information bit for SCell dormancy indication
is ACK for the first SLIV and
followed by NACK bits for the remaining SLIVs.
R1-2501376 Feature lead summary#3 on multi-cell scheduling with a
single DCI Moderator (Lenovo)
From Thursday session
Agreement
- Regarding
presence of UL-SCH field,
- 1 bit
UL-SCH field is always present in DCI format 0_3.
- UL-SCH
field and CSI request
field in a DCI format 0_3 are applied to the same PUSCH.
Agreement
- For NDI/RV indication in DCI format 0_3/1_3 for a TB,
- Within each block of NDI field, the NDI bits are placed in the
LSBs based on the SLIV position in the indicated
TDRA row. Padding bits, if any, are placed in the MSBs within the block.
- Within each block of RV field, the RV bits are placed in the
LSBs based on the SLIV position in the indicated
TDRA row. Padding bits, if any, are placed in the MSBs within the block.
Final summary in R1-2501377.
Placeholder only. RAN1 discussions on
9.12.2 will start in 2025.Q2. Please refer to RP-243317 for detailed scope of the WI for low band carrier aggregation via
switching.
Rapporteur to provide initial input on
higher layer signalling under agenda item 9.12. For input on higher layer
signalling from any other source, please include it as part of your tdoc to
relevant sub-agenda items.
R1-2503116 Session notes for 9.12 (Multi-Carrier Enhancements for NR
Phase 2) Ad-Hoc Chair (CMCC)
Friday decision: The session notes are endorsed and contents reflected below.
[120bis-R19-MCE] – Haipeng (Lenovo)
Email discussion on Rel-19 multi-carrier
enhancement
-
To be used for sharing updates on
online/offline schedule, details on what is to be discussed in online/offline
sessions, tdoc number of the moderator summary for online session, etc
R1-2501891 High layer parameters for Rel-19 Multi-Carrier Enhancements Lenovo
(Rapporteur)
Please refer to RP-242904 for detailed scope of
the WI for Multi-Carrier Enhancements for NR Phase 3.
R1-2501827 Discussion on enhancement of multi-cell PUSCH/PDSCH vivo
R1-2501885 Discussion on multi-cell PUSCH/PDSCH scheduling with a
single DCI Spreadtrum, UNISOC
R1-2501892 Discussion on multi-cell scheduling with a single DCI Lenovo
R1-2501910 Discussion on multi-cell PUSCH/PDSCH scheduling with a
single DCI ZTE Corporation, Sanechips
R1-2501960 Multi-cell PxSCH scheduling with a single DCI Ericsson
R1-2501977 Discussion on multi-cell PUSCH/PDSCH scheduling with a
single DCI CATT
R1-2502034 Discussion on multi-carrier enhancements for NR phase 3 China
Telecom
R1-2502215 Discussion on Rel-19 Multi-carrier enhancements Huawei,
HiSilicon
R1-2502282 Discussion of multi-cell scheduling with a single DCI OPPO
R1-2502388 Enhancements for multi-cell PUSCH/PDSCH scheduling Samsung
R1-2502484 Discussion on single DCI based multi-cell scheduling for
Rel-19 LG Electronics
R1-2502493 Discussion on multi-carrier enhancements for NR Phase 3 Panasonic
R1-2502495 Remaining details on Rel-19 Multi-carrier enhancements Nokia
R1-2502574 Discussion on Multi-cell PUSCHPDSCH scheduling with a
single DCI TCL
R1-2502998 Multi-carrier enhancements for NR phase 3 MediaTek Inc. (rev
of R1-2502720)
R1-2502783 Discussion on multi-cell PUSCH/PDSCH scheduling with a
single DCI NTT DOCOMO, INC.
R1-2502859 Multi-cell PUSCH/PDSCH scheduling with a single DCI Qualcomm
Incorporated
R1-2503037 Feature lead summary#1 on multi-cell scheduling with a
single DCI Moderator (Lenovo)
From Monday session
Conclusion
All bits in the NDI of TB1 and RV of TB1
corresponding to the cell with smallest serving cell index with invalid FDRA
are used for SCell dormancy indication.
Conclusion
For a DCI format 1_3 with fields repurposed
for SCell dormancy indication and without scheduling any PDSCH, one bit of ACK
is generated for SCell dormancy indication and included in the first
sub-codebook regardless of the number of SLIVs indicated by the DCI format 1_3
for the cell with fields repurposed for SCell dormancy indication.
Agreement
·
For a DCI format 1_3 with
fields repurposed for SCell dormancy indication and scheduling one or more
PDSCHs, if TDRA field indicates multiple SLIVs for the serving cell with
smallest serving cell index with invalid FDRA and nrofHARQ-BundlingGroups
is not provided for the serving cell, the HARQ-ACK information bit for SCell dormancy indication is ACK for the first SLIV and followed by NACK
bits for the remaining SLIVs.
·
For a DCI format 1_3 with
fields repurposed for SCell dormancy indication and scheduling one or more
PDSCHs, if TDRA field indicates multiple SLIVs for the serving cell with
smallest serving cell index with invalid FDRA and nrofHARQ-BundlingGroups is provided for the serving cell, the
HARQ-ACK information bit for SCell dormancy indication is ACK for the first TBG, and followed by NACK
bits for the remaining TBGs, if any.
·
Note: Related working
assumption made in RAN1#120 meeting does not need to be confirmed.
R1-2503038 Feature lead summary#2 on multi-cell scheduling with a
single DCI Moderator (Lenovo)
From Wednesday session
Agreement
For determining the number M of HARQ-ACK
information bits for each DCI format 1_3 corresponding to the second HARQ-ACK sub-codebook
in a PUCCH transmission:
·
M is a maximum number over all the configured cell set(s) S in
a PUCCH group of the sum of 
(if nrofHARQ-BundlingGroups is not provided for a serving
cell c) or 
(if nrofHARQ-BundlingGroups is provided for the serving cell
c) across serving cells of a respective cell set S that can be
co-scheduled by a DCI format 1_3;
o
is the maximum number of SLIVs amongst all rows of the multi-PDSCH
TDRA table configured on the active BWP of the serving cell c;
o
is the maximum number of transport block groups (TBGs) for first
TBs (and for second TBs, if configured) for the serving cell c if harq-ACKSpatialBundlingPUCCH
is not provided, or the maximum number of PDSCH reception groups on the serving
cell c if harq-ACKSpatialBundlingPUCCH is provided, and is
provided by RRC parameter nrofHARQ-BundlingGroups;
o
is the value of maxNrofCodeWordsScheduledByDCI for serving
cell c when harq-ACKSpatialBundlingPUCCH is not provided;
otherwise 
.
Final summary in R1-2503039.
Please refer to RP-250247 for detailed scope of
the WI for low band carrier aggregation via switching.
R1-2501828 Discussion on Low band carrier aggregation via switching vivo
R1-2501886 Discussion on low band carrier aggregation via switching Spreadtrum,
UNISOC
R1-2501893 Discussion on carrier switching pattern for low band
carrier aggregation via switching Lenovo
R1-2501911 Discussion on low band carrier aggregation via switching ZTE
Corporation, Sanechips
R1-2501978 Discussion on low band carrier aggregation via switching CATT
R1-2502046 Discussion on a low-band CA with switching Ofinno
R1-2502203 Discussion on low band carrier
aggregation via switching NEC Late submission
R1-2502216 Discussion on low band CA via switching Huawei,
HiSilicon
R1-2502283 Discussion of low-band CA via switching OPPO
R1-2502389 Discussion on low band carrier aggregation via switching Samsung
R1-2502426 Low band carrier aggregation through switching Ericsson
R1-2502485 Discussion on low band CA operation via switching for
Rel-19 LG Electronics
R1-2502496 Principles for low-band CA via switching Nokia
R1-2502575 Discussion on Low band carrier aggregation via switching TCL
R1-2502634 On low-band carrier aggregation via switching Apple
R1-2502721 Low band carrier aggregation via switching MediaTek Inc.
R1-2502784 Discussion on Low band carrier aggregation via switching NTT
DOCOMO, INC.
R1-2502860 Low band carrier aggregation via switching Qualcomm
Incorporated
R1-2502635 FL summary #1 of Low band carrier aggregation via switching Moderator
(Apple)
Presented in Monday session.
R1-2502636 FL summary #2 of Low band carrier aggregation via switching Moderator
(Apple)
From Wednesday session
Agreement
·
For Rel-19 low NR band
carrier aggregation via switching, support only semi-static configuration of
switching pattern to a UE based on UE-specific RRC configuration between the
following two cases,
o
Case 1: Tx/Rx on FDD
carrier 1 and no Rx on SDL carrier 2
o
Case 2: Rx on SDL carrier 2
and no Tx/Rx on FDD carrier 1
·
FDD carrier 1 is PCell and
SDL carrier 2 is SCell.
·
SCS 15KHz on both carriers.
Agreement
For
RRC configuration of semi-static switching pattern in Rel-19 low NR band
carrier aggregation via switching, it is not expected that the same slot (1ms)
contains both symbol(s) configured as FDD carrier and symbol(s) configured as
SDL carrier.
Agreement
For
Rel-19 low NR band carrier aggregation via switching, the semi-static switching
pattern and corresponding switching gap are based on the downlink timing (DL
reception time at UE side) of Pcell.
Agreement
For RRC configuration of
semi-static switching pattern in Rel-19 low NR band carrier aggregation via
switching, the time unit (resolution) of the semi-static switching pattern
configuration is slot (1ms for 15kHz SCS).
R1-2502637 FL summary #3 of Low band carrier aggregation via switching Moderator
(Apple)
From Thursday session
Agreement
- For
RRC configuration of semi-static switching pattern in Rel-19 low NR band
carrier aggregation via switching, support bitmap design
- NW
configures a periodicity, denoted as
slots, and a
bitmap of P bits. Each
bit in the bitmap indicates which carrier is configured for the
corresponding slot, ‘0’ indicates FDD carrier 1, and ‘1’ indicates SDL carrier 2.
- The pattern starts from the beginning of SFN 0
of PCell.
- Restriction of maximum X switch(es) within Y
slot(s).
- FFS: detailed value and relation of X and Y.
- FFS: other restriction.
Agreement
For RRC configuration of semi-static switching pattern in Rel-19
low NR band carrier aggregation via switching, regarding the location of the
switching gap,
- For switching from SDL carrier
to FDD carrier, the switching gap is always assumed at the “switch from”
carrier, i.e., SDL carrier.
- For switching from
FDD carrier to SDL carrier, down-select one of the following solutions:
- Alt 1: Switching
gap is always assumed at the “switch from” carrier, i.e., FDD carrier.
- Alt 2: NW
configures whether the switching gap is at the FDD carrier or SDL carrier.
- Alt 3: Switching
gap is always assumed at the SDL carrier.
Agreement
For
RRC configuration of semi-static switching pattern in Rel-19 low NR band
carrier aggregation via switching, semi-static switching pattern is periodic
with periodicity of P slots (ms), support P= 40 ms.
Agreement
For RRC configuration of semi-static switching pattern in Rel-19
low NR band carrier aggregation via switching, the duration of the switching
gap is RRC configured by the NW,
- Switching
gap duration can be different for FDD to SDL switch, and SDL to FDD
switch.
- Note: NW ensures that the switching gap is enough
to cover at least the switching period as in RAN4 LS (R1-2501702) and UL TA (if
needed).
- For the UL TA,
- Switching gap for SDL to FDD switch ends at the end
of slot on SDL.
- Note:
RAN1 assumes that switching
gap for
SDL
to FDD switch includes UL TA.
- FFS: whether it
has specification impact.
Final
summary in R1-2503110.
Rapporteur to provide initial input on
higher layer signalling under agenda item 9.12. For input on higher layer
signalling from any other source, please include it as part of your tdoc to
relevant sub-agenda items.
R1-2504898 Session
notes for 9.12 (Multi-Carrier Enhancements for NR Phase 2) Ad-Hoc Chair (CMCC)
Endorsed and
incorporated below.
[121-R19-MCE] Email
discussion on Rel-19 multi-carrier enhancement – Haipeng (Lenovo)
-
To be used
for sharing updates on online/offline schedule, details on what is to be
discussed in online/offline sessions, tdoc number of the moderator summary for
online session, etc
R1-2503655 Updated high layer parameters for
Rel-19 Multi-Carrier Enhancements Lenovo (Rapporteur)
Please refer to RP-242904
for detailed scope of the WI for Multi-Carrier Enhancements for NR Phase 3.
Agreement
•
Below TP for TS38.300 is adopted for Rel-19 MCE.
|
10.11 Multi-cell scheduling by a single DCI
Multi-cell
scheduling by a single DCI allows the PDCCH of a serving cell to schedule
PDSCH(s)/PUSCH(s) on one or more serving cells with the single DCI but with
the following restrictions:
- When
a serving cell is configured with a PDCCH which schedules PDSCH(s)/PUSCH(s)
on a cell set, the PUSCH/PDSCH on serving cells in the cell set is always
scheduled by a PDCCH on the serving cell;
- When
SpCell is configured with a PDCCH which schedules PDSCH(s)/PUSCH(s) on
serving cells in a cell set, that SpCell's PDSCH and PUSCH cannot be
scheduled by a PDCCH on an SCell;
- When
an SCell is configured with a PDCCH which schedules PDSCH(s)/PUSCH(s) on
serving cells in a cell set, SpCell is not included in the cell set;
- The
scheduling PDCCH and the scheduled PDSCH(s)/PUSCH(s) can use the same or
different numerologies;
- The
co-scheduled PDSCH(s) with a PDCCH can use the same or different
numerologies;
- The
co-scheduled PUSCH(s) with a PDCCH can use the same or different
numerologies.
|
•
Send an LS to RAN2 to convey the above TP.
Agreement
•
For a cell within a cell set configured to be schedulable by a DCI
format 0_3, the network does not configure pusch-TimeDomainAllocationListForMultiPUSCH-DCI-0-3
simultaneously with the numberOfSlotsTBoMS-r17 and/or pusch-AggregationFactor.
•
Add above to RRC parameter list.
Agreement
Agreement
•
For Type-2 HARQ-ACK
codebook, adopt TP1 in Section 8 of R1-2504761 to
Section 9.1.3.1, TS38.213.
Agreement
For PUCCH power control, adopt TP2A in
Section 8 of R1-2504761 to Section 9.1.3.1, TS38.213.
Agreement
•
Support maximum 64 rows for TDRA-FieldIndexListDCI-1-3-r19.
•
Support maximum 128 rows for TDRA-FieldIndexListDCI-0-3-r19.
Agreement
Draft
LS R1-2504764 is endorsed in principle.
Agreement
Final
LS R1-2504861 is endorsed.
R1-2504764 Draft LS on TS38.300
TP for Multi-carrier enhancements in Rel-19
R1-2504761 Feature lead summary
#1 on multi-cell scheduling with a single DCI Moderator (Lenovo)
R1-2503271 Discussion on Rel-19
Multi-carrier enhancements Huawei, HiSilicon
R1-2503330 Discussion on
multi-cell PUSCH/PDSCH scheduling with a single DCI ZTE
Corporation, Sanechips
R1-2503383 Remaining issues on
enhancement of multi-cell PUSCH and PDSCH scheduling with a single DCI vivo
R1-2503429 Remaining details on
Rel-19 Multi-carrier enhancements Nokia
R1-2503587 Enhancements for
multi-cell PUSCH/PDSCH scheduling Samsung
R1-2503607 Multi-cell PxSCH
scheduling with a single DCI Ericsson
R1-2503656 Discussion on
multi-cell scheduling with a single DCI Lenovo
R1-2503779 Discussion on
multi-cell PUSCH/PDSCH scheduling with a single DCI CATT
R1-2503990 Discussion on
multi-carrier enhancements for NR Phase 3 Panasonic
R1-2504056 Remaining issues on
multi-carrier enhancements for NR phase 3 China Telecom
R1-2504216 Discussion of
multi-cell scheduling with a single DCI OPPO
R1-2504254 Discussion on single
DCI based multi-cell scheduling for Rel-19 LG Electronics
R1-2504274 Multi-carrier
enhancements for NR phase 2 MediaTek Inc.
R1-2504415 Multi-cell
PUSCH/PDSCH scheduling with a single DCI Qualcomm Incorporated
R1-2504519 Discussion on
multi-cell PUSCH/PDSCH scheduling with a single DCI NTT DOCOMO,
INC.
Please refer to RP-250247
for detailed scope of the WI for low band carrier aggregation via switching.
Agreement
For Rel-19 low NR band
carrier aggregation via switching, support configuration of only one switching
pattern to a UE based on UE-specific RRC configuration.
Agreement
For RRC configuration
of semi-static switching pattern in Rel-19 low NR band carrier aggregation via
switching, regarding the location of the switching gap for switching from FDD
carrier to SDL carrier, only support the switching
gap is located at the “switch from” carrier, i.e., FDD carrier.
·
Switching gap ends at the
end of the last slot on the “switch from” carrier
Agreement
Draft LS R1-2504868 is endorsed in principle.
Agreement
Final LS R1-2504869 is endorsed.
Agreement
·
For
Rel-19 low NR band carrier aggregation via switching, in terms of the collision
handling
o The following cases for
collision handling are specified where UL TA is assumed to be 0 for the
determination of overlapping. The UL TA =0 assumption only applies to the UL
transmission configured by higher layer
§ Collision 1: If a UE is
configured by higher layers to transmit a PUSCH, PUCCH, PRACH, or SRS in a set of symbols of an UL
slot on the FDD carrier that overlaps, even partially, with the set of symbols
of the switching gap, the UE does not transmit the PUSCH, PUCCH, PRACH, or SRS
§ Collision 2: If a UE is configured by
higher layers to transmit a PUSCH, PUCCH, PRACH, or SRS in a set of symbols of
an UL slot on the FDD carrier that overlaps, even partially, with the set of
symbols of the DL slot indicated as SDL carrier, the UE does not transmit the
PUSCH, PUCCH, PRACH, or SRS
§ Collision 3: If a UE is configured by
higher layers to receive a PDCCH, PDSCH, PRS or CSI-RS in a set of symbols of a
DL slot on the SDL carrier that overlaps, even partially, with the set of
symbols of the switching gap, the UE does not receive the PDCCH, PDSCH, PRS or
CSI-RS.
§ Collision 4: If a UE is configured by
higher layers to receive a PDCCH, PDSCH, PRS or CSI-RS in a set of symbols of a
DL slot on the SDL carrier that overlaps, even partially, with the set of
symbols of the DL slot indicated as FDD carrier, the UE does not receive the
PDCCH, PDSCH, PRS or CSI-RS
§ Collision 5: If a UE is configured by
higher layers to receive a PDCCH, PDSCH, PRS or CSI-RS in a set of symbols of a
DL slot on the FDD carrier that overlaps, even partially, with the set of
symbols of the switching gap, the UE does not receive the PDCCH, PDSCH, PRS or
CSI-RS.
§ Collision 6: If a UE is configured by
higher layers to receive a PDCCH, PDSCH, PRS or CSI-RS in a set of symbols of a
DL slot on the FDD carrier that overlaps, even partially, with the set of
symbols of the DL slot indicated as SDL carrier, the UE does not receive the
PDCCH, PDSCH, PRS or CSI-RS
o For the other cases, i.e., DL and UL
signals/channels scheduled/triggered by DCI
§ A UE is not expected any
scheduling/triggering from network that will lead to above collisions
·
Except
that the PUSCH, PUCCH, PRACH, or SRS transmission that overlapped with the switching gap on SDL carrier when the SDL carrier switches to
FDD carrier is not considered as collision
·
UE
expects that the switching gap configured by the NW for SDL carrier to FDD
carrier switching covers at least the switching period as in RAN4 LS
(R1-2501702) and UL TA
R1-2504868 Draft
LS on Low NR band carrier aggregation via switching Apple [RAN1]
R1-2504350 FL summary #3 of Low band carrier
aggregation via switching Moderator (Apple)
R1-2504349 FL summary #2 of
Low band carrier aggregation via switching Moderator
(Apple)
R1-2504348 FL summary #1 of
Low band carrier aggregation via switching Moderator
(Apple)
R1-2503273 Discussion on low
band CA via switching Huawei, HiSilicon
R1-2503331 Discussion on low band
carrier aggregation via switching ZTE Corporation, Sanechips
R1-2503384 Remaining issues on
Low band carrier aggregation via switching vivo
R1-2503421 Discussion on low
band carrier aggregation via switching NEC
R1-2503430 On low-band CA via
switching Nokia
R1-2503532 Discussion on low
band carrier aggregation via switching Spreadtrum, UNISOC
R1-2503588 Discussion on low
band carrier aggregation via switching Samsung
R1-2503657 Discussion on carrier
switching pattern for low band carrier aggregation via switching Lenovo
R1-2503739 Discussion on a
low-band CA with switching Ofinno
R1-2503780 Discussion on low
band carrier aggregation via switching CATT
R1-2504153 Low band carrier
aggregation via switching ETRI
R1-2504217 Discussion of
low-band CA via switching OPPO
R1-2504255 Discussion on low
band CA operation via switching for Rel-19 LG Electronics
R1-2504275 Low band carrier
aggregation via switching MediaTek Inc.
R1-2504347 On low band carrier
aggregation via switching Apple
R1-2504348 FL summary #1 of Low
band carrier aggregation via switching Moderator (Apple)
R1-2504349 FL summary #2 of Low
band carrier aggregation via switching Moderator (Apple)
R1-2504350 FL summary #3 of Low
band carrier aggregation via switching Moderator (Apple)
R1-2504416 Low-band carrier
aggregation via switching Qualcomm Incorporated
R1-2504440 Low band carrier
aggregation through switching Ericsson
R1-2504520 Discussion on Low
band carrier aggregation via switching NTT DOCOMO, INC.
R1-2504606 On Low band carrier
aggregation via switching Google Ireland Limited